ATI Technologies Inc.,
3761 Victoria Park Avenue
Scarborough, Ontario, M1W 3S2
Tel:(416)756-0718 Fax:(416) 756-0720
CompuServe: ATI Support 74740,667  GO ATITECH

ATI Mach32 Troubleshooting Tips

Driver Updates
On Disk: $10-15 S&H
ATI BBS: 416-756-4591
CompuServe: GO ATITECH,
Library 17

Contents:

Trouble Booting
Trouble with the INSTALL Program
Trouble with DOS Applications
Trouble with Windows
Trouble with Screen Sizing and/or Positioning, "Mode Not
       Supported" or "Insufficient Memory" Error Messages
Contacting ATI Customer Support, Reporting Driver Bugs and
Obtaining Technical Assistance
Obtaining Further Information


Trouble Booting:

Check the CMOS setup (usually the "advanced" section) for
"shadow" and "cache" functions in the C000-C7FF region.  Try
disabling these features.

Remove or disable any other video systems in the machine.  The
Graphics Ultra+ has an onboard VGA subsystem which cannot be
disabled.  Dual adapter configurations are possible with MDA and
CGA adapters, but make sure that the Mach32 card is functioning
on its own before attempting such configurations.

The Graphics Ultra Pro and Mach32 VLB cards have VGA subsystems
which may be disabled through DIP switch settings.  Make sure
that the card is functioning normally with the VGA functions
enabled before attempting a dual adapter configuration with a
second (VGA) adapter.

Ensure that the 2E0-2EF I/O ports are free for use by the Mach32
accelerator.  This range includes the standard COM4 base address
of 2E8.  Typical peripherals to check include internal modems,
network adapters, SCSI host adapters and proprietary scanner
interfaces.  If in doubt, remove these cards from the machine to
test.  The Mach32 cards will behave erratically if the 2E0-2EF
ports are in use by another peripheral.

Try a "clean boot" with no AUTOEXEC.BAT or CONFIG.SYS files.  If
you can get the machine up this way, check these system files for
potentially troublesome devices and TSR (terminate and stay
resident) utilities.  If you find the RAMBIOS and/or VANSI
devices in CONFIG.SYS, remove them.  Any other devices which
might affect the video system (screen savers, MODE CON commands,
etc.) should be removed as well.

If the machine still won't boot, try it in an 8-bit slot.  This
reduces the number of enhanced features that will be active on
the card as it powers up.  If a second machine is available, try
it there, and reset the card to its factory defaults using the
TEST program, as shown:

TEST /f


Trouble with the INSTALL Program:

The INSTALL program must be used to set the operating
characteristics for the card and to install the drivers and
utilities.  The factory default settings of the card are
sufficient for operation as a VGA card, but advanced features
must be enabled in INSTALL.

If INSTALL reports that it cannot locate the card, or that the
card's ROM is "out of date", disable your memory manager and
check for a hardware conflict in the 2E0-2EF region, as outlined
above in the "Trouble Booting" section.


Specific items on the "Set Power Up Configuration" menu of
INSTALL are explained here.  Not all versions of INSTALL will
show every selection.


MONITOR TYPE: This setting defaults to "VGA" which will allow
only the 640x480 resolution.  You must change the monitor type to
match your actual monitor in order to access the higher
resolutions available on the Mach32.

If your monitor is not listed as a preset "type" you may need to
perform a "CUSTOM" monitor setup.  Check your monitor manual to
determine: a) the maximum resolution, b) the horizontal scanning
frequencies supported, c) the vertical scanning frequencies
supported.

Some monitor manufacturers provide a table of suggested refresh
rates for each resolution.  If this is the case in your manual,
use those suggestions to configure each resolution on the CUSTOM
setup menu.

If the monitor manual provides only the scanning frequencies, use
the horizontal frequencies as a guide in choosing the appropriate
refresh rates for each resolution.  Higher refresh rates put an
increased strain on the monitor circuitry.  Do not exceed the
manufacturer's suggested settings.

There is a complete list of monitor signals supported in the back
of your ATI manual.  They are reproduced here for your
convenience.  Some models of the Mach32 accelerators may not
support all of the modes shown.  Signals are listed as kHz
Horizontal/Hz Vertical.  Interlaced modes are represented with an
"i".
                       
640x480:   IBM default (31.5/60), 37.7/72, 44.6/72
800x600:   31.5/89i, 33.8/95i, 35.2/56, 37.9/60, 44.5/70,
             48.0/72, 52.4/76
1024x768:  35.5/87i, 48.4/60, 53.9/66, 56.1/70, 57.9/72, 61.4/76
1280x1024: 50.0/87i, 50.0/95i, 64.0/60, 74.6/70, 81.1/74

If your monitor does not support one or more of the resolutions
available on the CUSTOM setup menu, be sure to configure those
resolutions as "Not Supported".

If any of the CUSTOM setup screens do not appear, or seem to
operate erratically, try disabling your memory manager until the
configuration is complete.


POWER UP VIDEO MODE: The default VGA(CV80) setting provides an
enhanced VGA character set in the standard 80x25 character
format.  Earlier standards are provided, but are not generally
necessary.  Extended text modes (such as 132x25) are only
available on the "Set Current Video Mode" menu.


ROM ACCESS: The default (8-bit) setting is recommended for
hardware compatibility reasons.  Generally the ROMs are
"shadowed" directly by the system hardware, or through the
shadowing capabilities of the memory manager, so the 16-bit
setting is not required.  Some systems may hang at boot time if
16-bit ROM access is enabled.


MOUSE CONFIGURATION: The default setting for the mouse port is
"disabled".  When configuring your mouse, keep the following
standards in mind.  Erratic system behaviour may result if you
have more than one device configured to use the same IRQ line or
I/O address.

Two mouse port addresses are provided for increased flexibility. 
The Primary address is recommended for maximal software
compatibility.

IRQ 5 is generally used by LPT2 (the second printer port).  IRQ 5
is the recommended mouse IRQ for systems which have only a single
printer port.
IRQ 4 is normally shared by the COM1 and COM2 serial ports.
IRQ 3 is normally shared by the COM2 and COM4 serial ports.
IRQ 2 is "cascaded" to a secondary interrupt controller on the
motherboard.  In some cases it is available as a "virtual" IRQ 9,
in others the use of IRQ 2 can cause the system to hang.

It is highly recommended that you refrain from installing a mouse
driver in CONFIG.SYS or AUTOEXEC.BAT until you have tested the
mouse port functions.  The MOUSE.COM version of the driver can be
run manually after boot by typing "MOUSE" at the DOS prompt.

In some circumstances it may be necessary to disable the mouse
port at a hardware level, to avoid conflicts with another similar
mouse interface in the system.  Opening jumper JU18 on our Mach32
boards will disable the mouse port, overriding any software
settings.


VGA BUS I/O: The default setting (8-bit) uses only half of the
data transfer capacity of the ISA bus.  The 8-bit setting is
required in "dual adapter" systems, where access to the video
memory areas is shared with a CGA, MDA or VGA adapter.  In most
other cases, the 16-bit setting is preferable.  Some systems may
lock up when forced into 16-bit bus I/O, so ensure that you've
got an 8-bit slot or a second system available to aid in
resetting the card.


MEMORY APERTURE: The "memory aperture" feature of our ISA Mach32
products can only be enabled in systems having less than 12MB of
RAM installed.  This is due to the 16MB address limitation on the
ISA bus.  Our memory aperture can be enabled only within the
addressable space on the bus.  If this space is occupied by
system RAM it is impossible to have the "aperture" share this
area.

There is a feature in the INSTALL program which checks to see how
much memory is in the system.  If 16MB are detected in an ISA
system, INSTALL will display a warning.  Unfortunately there is a
bug in the current version of INSTALL which causes it to display
the warning message whether you've attempted to enable the
"memory aperture" feature or not.

If you have an ISA system with less than 12MB of RAM installed
and the Memory Aperture feature will not enable, there is likely
a problem either with the memory manager, or with the motherboard
DIP switches or jumpers.  Disable the memory manager and try
again.  If this doesn't help, check the CMOS setup to be sure
that the correct amount of system RAM is being reported.

Try the fixes shown in "Trouble Booting", and make sure that the
CMOS is not set to "cache" the memory area in which the Mach32
memory aperture will be installed.  Some CMOS setups allow you to
define a "cachable memory size" option.  Make sure that this is
set to the actual amount of RAM installed.  Other setup routines
will allow you to define a "non cachable block".  If this is how
your CMOS operates, be sure to define the memory aperture
location as a "non cachable block".  It may be necessary to
adjust the motherboard DIP switches or jumpers to properly
reflect the amount of system RAM installed.  Check your
motherboard manual for details.

On an ISA system, the default aperture state is "disabled".  The
default positioning of the aperture, once enabled, is at the 10MB
location.  We have found that the 12MB is more appropriate for
systems in which a "non-cachable block" must be defined in the
CMOS.  The aperture size will be 4MB for a 2MB Mach32, and 2MB
for a 1MB Mach32.

Mach32 products designed for other bus specifications (EISA, 32-
bit MicroChannel, and VESA Local Bus) fall under the same sort of
limitations as the ISA models, but the maximum memory address on
these architectures is much higher (128MB), so the possibility of
a conflict with installed system RAM is slight.  We are currently
shipping a VLB (VESA Local Bus) version of the Mach32 through a
variety of OEM system builders, including Micronics and Gateway
2000.  A retail version of the VLB card has been announced, but
no date is yet set for release.  EISA boards began shipping in
early March and a 32-bit MCA version of the Mach32 should be
available shortly.

The recommended memory aperture location for the EISA and VLB
Mach32 products is at the default 100MB setting.  Only in
extremely "high-end" systems should it be necessary to move the
aperture to allow for more system RAM.

Early versions of the Mach32 Windows driver did not operate if
the memory aperture was disabled.  This problem has been resolved
in more recent versions of the driver.


ZERO WAIT STATE VGA: Some systems require that CPU-idle "wait
states" be added to RAM access operations.  Check your
motherboard documentation to see if this is the case with your
machine.  DO NOT attempt to enable Zero Wait State VGA in a
system which uses wait state cycles when accessing the system
RAM.  Erratic operation, scrambled DOS screens and system lockup
may result.


VGA MEMORY SIZE: Recommended values for this setting depend on
the total memory available on the Mach32 video adapter.  

On a 1MB Mach32 card, the "shared" setting is recommended, as it
allows the accelerator functions of the Mach32 access to the full
1MB memory pool.  Problems may result in this configuration,
however, as the VGA functions will have access to the same bank
of memory.  Applications which maintain simultaneous text and
accelerated graphics screens (such as ACAD and Windows) may cause
distortion of the screen data in the "shared" setting.  Try the
512k setting if you experience this problem.  The 512k option
will separate the VGA display memory from the accelerator display
memory, and still allow you to display 1024x768 @ 16 colours
under a standard 8514/a driver.

On a 2MB Mach32 card, it is possible to allocate a small amount
of video memory (eg 256k) for the sole use of the VGA functions
of the Mach32.  This will avoid the above-mentioned interference
problem and still leave a large bank of video RAM for use by the
accelerator.  Note, however, that applications which use a VGA,
ATI VGA Wonder or VESA SVGA interface may require more than 256k
of VGA memory available.  Try the larger settings, or switch into
"shared" mode if you experience this problem.

Keep in mind that certain ATI drivers may override the VGA Memory
Size setting in order to gain access to the full bank of video
memory.  The Mach32 Windows driver is a good example.  If it
becomes necessary to prevent this from happening, set
VGAShared=off in the [Mach32] section of the WIN.INI file.  Note
that this option is only available in a "Memory Aperture Enabled"
configuration.


Trouble with DOS Applications:

Try the tips shown in the "Trouble Booting" section.  Often
interference by a "shadow" or "cache" function will show up in a
text mode DOS application.

Ensure that your memory manager is not relocating the video ROM
through a "stealth" or "VGASwap" function.  At the very least,
you should "exclude" the ROM location (the default is C000-C7FF)
from use by the memory manager.  Some memory managers offer
special switches that will protect the ROM from "stealth-type"
functions (eg XST in QEMM).  Check your memory manager manual for
details.

Determine the nature of the video interface expected by the DOS
application.  Is it VGA text, VGA graphics, ATI VGA Wonder, VESA
SVGA, IBM 8514/a, ATI Mach8 or ATI Mach32?  

VGA, ATI VGA Wonder and VESA SVGA interfaces rely on the onboard
VGA subsystem (or the external VGA adapter in a dual adapter
configuration).  In a standard installation, these interfaces
rely on the "VGA Memory Size" setting in the INSTALL program.  A
"shared" setting will allocate up to 1MB of video memory for
these functions, the maximum addressable by the VGA circuitry in
the Mach32 chipset.  As noted under VGA MEMORY SIZE, in "Trouble
with the INSTALL Program", other settings may be appropriate for
specific applications.

Applications which expect a VESA SVGA interface will often
require that the VVESA.COM TSR (terminate and stay resident
program) be executed first.

IBM 8514/a defines an accelerated video standard which is
typically presented as 1024x768 @ 256 colours.  Some applications
that use this standard will interact directly with the Mach32 on
a hardware level, while others will require the Turbo AI
(application interface) to be loaded first.  The Turbo AI is
installed, by default, as \HDIPCDOS\HDILOAD.EXE and operates in a
TSR fashion, like the VESA interface.

For an 8514/a application to display 1024x768 @ 256 colours, it
will require access to a 1M bank of accelerator memory.  Some
applications may also support a 512k bank, offering 16 colours at
this resolution.  See VGA MEMORY SIZE, in the "Trouble with the
INSTALL Program" section, for further information.

IBM 8514/a, ATI Mach8 and ATI Mach32 interfaces use the
accelerator functions of the Mach32 chipset.  Applications which
directly support the ATI 8514/Ultra, Graphics Ultra, Graphics
Ultra+ or Graphics Ultra Pro will generally not require the
HDILOAD TSR.

In some cases, switching from one interface to another (from
8514/a to Mach32 for example) will result in unusual behaviour of
the video system.  On a Mach32 product, this can generally be
remedied by using a special function of the TEST program to re-
initialize the graphics card before entering the second
application:

TEST /i


Trouble with Windows:

Try the adjustments to the memory manager line shown in the DOS
section.  Also, try inserting the following line in the [386Enh]
section of the SYSTEM.INI file:

EMMExclude=A000-C7FF

Check the version of the Mach32 Windows driver, as shown on the
FlexDesk Control Panel.  As of March 4, 1993, our latest driver
release is version 1.1(55).

Check the "README" file which came with the driver, for a
possible solution.  Under Windows, open the README icon in the
Mach32 Utilities group.  In DOS, read the M32PANEL.TXT file.

Try an alternate Windows driver, to determine whether the problem
is isolated.  If you have access to them, try the ATI Mach8
drivers.  If your monitor supports the 1024x768 resolution, try
the Microsoft 8514/a driver.  As a final check, try the Microsoft
VGA driver.

Some early versions of the Mach32 Windows installation procedure
caused undesirable changes in the SYSTEM.INI file.  If you
experience problems starting Windows, check that the following
entries in the [386Enh] section of SYSTEM.INI are intact:

device=vtdapi.386           (absence causes "MCI timer" error)
device=*int13          (absence causes "virtual device" error)

Many of our customers report difficulties with WordPerfect for
Windows.  This application requires a special command line switch
to run properly with an accelerated video card.  This "flash"
option was added in the late April 1992 release of WordPerfect
for Windows, and has been available in all subsequent releases.

Check your current WP command line by highlighting the WP icon
and pressing ALT-ENTER.  Change it to read as follows:

[path] WPWIN.EXE /fl

This should help the program run more smoothly, and speed it up
somewhat as well.



Trouble with Screen Sizing and/or Positioning, "Mode Not
Supported" or "Insufficient Memory" Error Messages:

It is vital that the MONITOR TYPE selection on the "set power up
configuration" menu of the INSTALL program properly match your
monitor.  The VGA MEMORY SIZE setting may also impact on the
amount of video memory available to certain applications.  See
"Trouble with the INSTALL Program" for details.

Similar error messages may be displayed if the driver/application
cannot locate the ROM BIOS code for the Mach32 card.  It is
essential that you prevent your memory manager from performing
"stealth" or "VGASwap" functions on the video ROM.  If you
require that a "stealth" function be active for the other ROMs in
the system, ensure that the video ROM is protected.  Check your
memory manager manual for details.  See "Trouble with DOS
Applications" for more information.


Contacting ATI Customer Support, Reporting Driver Bugs
and Obtaining Technical Assistance:

Please be sure to have all relevant information available when
contacting ATI Customer Support.  Of particular importance to us
is the BIOS Part Number of your ATI product.

The BIOS part number is available on a white sticker attached to
the ROM chip on your ATI card, and is posted on the screen at
boot time.  ATI Mach32 products come with a "C-INFO" utility
which will also report the BIOS part number.  The "Show System
Information" selection on the "Test" menu of your ATI
installation software will perform a similar function.  Please
record your BIOS part number in your ATI manual.  It is extremely
helpful to us in identifying your specific ATI product.

We are continually updating our driver support, especially for
Windows 3.1.  Bug reports are welcome, by fax and through our
CompuServe email account.  Obtaining technical support through
our fax and email channels requires that we receive as much
information as possible.  Please ensure that your report contains
the following information:  

-Name and BIOS part number of your ATI product, and amount of
video memory installed
-version of the Windows driver release (as reported on the
       FlexDesk Control Panel)
-name, version and release date of all software involved
-CPU type (eg. 286/12, 386sx/16, 486dx2/66) 
-amount of system RAM installed
-monitor attached
-current settings on the "Set Power Up Configuration" screen of
your ATI INSTALL program
-relevant sections from the WIN.INI file: [Mach32]
-relevant sections of the SYSTEM.INI file: [boot] and [386Enh]
-CONFIG.SYS and AUTOEXEC.BAT
-a detailed list of steps required to reproduce the problem
-for installation-related problems, please also include a list of
       other adapters in the machine with configuration information
       for each item

Please check any relevant "README" files for a solution before
reporting driver bugs.


Obtaining Further Information:

Additional documents, which cover specific aspects of Mach32
configuration, are available upon request.  For quicker service,
please quote both the "technote number" and the title of the
document.

TN067:  Mach32 Memory Aperture Configuration Issues
TN068:  Using CUSTOM Monitor Configuration
TN069:  Memory Manager Configurations
TN070:  Graphics Ultra Pro/+ Windows Installation Hints
TN074:  Mach32 Programmer's Reference Manual Information
